-
Notifications
You must be signed in to change notification settings - Fork 32
🎨Storage with Celery: unit tests working now with storage worker implemented #7438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🎨Storage with Celery: unit tests working now with storage worker implemented #7438
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7438 +/- ##
==========================================
+ Coverage 87.32% 87.44% +0.11%
==========================================
Files 1714 1708 -6
Lines 66602 66423 -179
Branches 1131 1132 +1
==========================================
- Hits 58159 58082 -77
+ Misses 8121 8020 -101
+ Partials 322 321 -1
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
bisgaard-itis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice. Thanks a lot!
|
pcrespov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
go go go



What do these changes do?
this PR sets up the base framework for testing storage with a storage celery worker (fixture
with_storage_celery_worker)test/modules/celery--> gonetest_modules_celery.pynow there with example on how to use it@giancarloromeo now needs to use the redis/rabbitmq instead of cache:memory I guess.
Related issue/s
How to test
Dev-ops checklist